fix: handle SAML/SSO HTML responses in API version fallback#20
Merged
Conversation
JIRA Data Center with SSO (e.g. Okta SAML) returns HTML redirect pages with 200 OK on unsupported API v3 endpoints instead of a proper error. This caused displayIssueDetails to crash accessing fields on a string. - Detect non-JSON (HTML/string) responses in requestApi and auto-fallback - Add guard checks in displayIssueDetails and formatIssueAsMarkdown
github-actions bot
pushed a commit
that referenced
this pull request
Apr 1, 2026
## [2.3.2](v2.3.1...v2.3.2) (2026-04-01) ### Bug Fixes * handle SAML/SSO HTML responses in API version fallback ([#20](#20)) ([840b608](840b608))
|
🎉 This PR is included in version 2.3.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
JIRA Data Center with SSO (Okta SAML) returns HTML redirect pages with 200 OK on unsupported API v3 endpoints. This caused
displayIssueDetailsto crash withCannot read properties of undefined (reading 'summary').Type of Change
Changes Made
requestApiand auto-fallback to the other API versiondisplayIssueDetailsandformatIssueAsMarkdownwith actionable error messagesTesting
Test Results
Deployment Notes
Checklist